<para>
A list of modules to load. Note that GTK+ also allows to specify modules to load via a commandline option (<option>--gtk-module</option>) and with the <literal>gtk-modules</literal> setting.
</para>
+ <warning>
+ Note that this environment variable is read by GTK+ 2.x too,
+ which may not have the same set of modules available for loading.
+ </warning>
</formalpara>
<formalpara>
modules, file system backends and print backends. If the path to
the dynamically loaded object is given as an absolute path name,
then GTK+ loads it directly.
- Otherwise, GTK+ goes in turn through the directories in GTK_PATH,
+ Otherwise, GTK+ goes in turn through the directories in <envar>GTK_PATH</envar>,
followed by the directory <filename>.gtk-3.0</filename> in the user's
home directory, followed by the system default directory,
which is <filename><replaceable>libdir</replaceable>/gtk-3.0/modules</filename>.
The components of GTK_PATH are separated by the ':' character on
Linux and Unix, and the ';' character on Windows.
</para>
+ <warning>
+ Note that this environment variable is read by GTK+ 2.x too, which
+ makes it unsuitable for setting it system-wide (or session-wide),
+ since doing so will cause either GTK+ 2.x applications or GTK+ 3
+ applications to see incompatible modules.
+ </warning>
</formalpara>
<formalpara>
The <filename>immodules.cache</filename> file is generated by the
<command>gtk-query-immodules-3.0</command> utility.
</para>
+ <warning>
+ Note that this environment variable is read by GTK+ 2.x too, which
+ makes it unsuitable for setting it system-wide (or session-wide),
+ since doing so will cause either GTK+ 2.x applications or GTK+ 3
+ applications to see the wrong list of IM modules.
+ </warning>
</formalpara>
<formalpara>